Skip to content

chore: regenerate schema from upstream spec - #57

Merged
cubehouse merged 3 commits into
mainfrom
automated/spec-drift
Oct 30, 2026
Merged

cubehouse merged 3 commits into
mainfrom
automated/spec-drift

Conversation

@tpw-drift

@tpw-drift tpw-drift Bot commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Automated schema regeneration from the api.themeparks.wiki OpenAPI spec.

  • build: success
  • live smoke tests: success

A build failure here means the upstream contract changed in a way
this client cannot absorb automatically. Do not merge until it is
green.

@tpw-drift
tpw-drift Bot force-pushed the automated/spec-drift branch 3 times, most recently from cb6777a to f1d80cd Compare October 7, 2026 13:27
@tpw-drift
tpw-drift Bot force-pushed the automated/spec-drift branch from f1d80cd to 8debed5 Compare October 27, 2026 12:15
cubehouse and others added 2 commits October 30, 2026 20:46
The regenerated schema adds implausibleWaits and inParkHours.implausibleWaits,
each with standby and singleRider counts, so the CSV now has 45 columns. The
new ones sit after extremeWaitsSingleRider and after
inParkHoursExtremeWaitsSingleRider, so the fingerprint changes and any
in-flight resume is refused.

csv_contract.json is the copy shared with the Python SDK and is
byte-identical there (same 45 columns, same fingerprint 8cbd164fcfb9698c).

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@cubehouse
cubehouse merged commit 18dea20 into main Oct 30, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant